[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] DNSconfig questions
- Subject: Re: [cobalt-users] DNSconfig questions
- From: "Gerald Waugh" <gerald@xxxxxxxxx>
- Date: Thu Jun 21 08:08:10 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> >
> > What happens if you run:
> > dig mydomain.com @dns1.zzzzzzz.org
> responses are edited for security:
> [root@ries-knight /root]# ping mydomain.com
> ping: unknown host mydomain.com
>
> [root@ries-knight /root]# dig mydomain.com@xxxxxxxxxxxx
You did leave a space between "mydomain.com" and '@' didn't
you?
> ; <<>> DiG 9.1.1 <<>> mydomain.com@xxxxxxxxxxxx
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id:
555555
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1,
ADDITIONAL: 0
>
Notice that status = NXDOMAIN
That means non-existent domain.
Your nameserver is not loading the zone?
Do a "ndc" reload of the domain or do
a "ndc restart"
Then do a "tail -n 100 /var/log/messages"
- shows the last 100 lines -
Look and see if the zone was loaded OK.
Gerald
P.S. Regardless of propagation the command
dig mydomain.com @mynmaeserver.com
Should work.