[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] DNSconfig questions



It turns out that the COLO the box is located in is closing shop for that
physical location.  It's connection was turned off this week.

arrgh!

Bill
>
> 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.
>
>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>