Strange Resolution Problem
Simon at wretched.demon.co.uk
Mon Dec 16 23:51:12 UTC 2002
Ruben I Safir wrote:
> Other machines can not resolve the name, including the host itself:
> david:~ # dig daivd.rm-cpa.com
You got the name wrong in this example, which doesn't help.
daivd != david
Your zone doesn't list; www2.mrbrklyn.com. as a name server for
the zone. This isn't your problem, but you might want to fix it
anyway, not much point having two name servers if things breaks
when mail.rm-cpa.com stops answering.
It is considered "bad form" to have RFC1918 address in public
zone files, although if people don't know their names it
shouldn't be an issue.
Otherwise the zone looks correctly delegated, and should work
correctly, I suspect client configuration issues.
> DRM is THEFT - We are the STAKEHOLDERS http://fairuse.nylxs.com
More information about the bind-users