Help, settling this dispute!

[Kevin Darcy]

The configuration is flawed, in that omar.hosting-network.com is a single point
of failure for the domain. But under normal circumstances, everything should
work: omar.hosting-network.com should always resolve since a glue record exists
for it, and dns1.featureprice.com and dns2.featureprice.com are both answering
authoritative for the zone and seem to have up-to-date copies. He should make
the delegations and the in-zone NS records match, though, preferably listing all
3 servers in both places.


- Kevin

Gerald Waugh wrote:

> An acquaintance of mine has a domain named thebird.org. He is having problems
> with email.
> I think his DNS records are screwed up, but he insist they are OK, and is
> blaming procmail.
> I told him to get the DNS fixed first. Am I wrong?
>
> -------- Whois query yields nameservers; -------
>    DNS1.FEATUREPRICE.COM 216.85.166.92
>    DNS2.FEATUREPRICE.COM 216.207.41.114
>
> ; <<>> DiG 8.2 <<>> thebird.org
> ;; ANSWER SECTION:
> thebird.org.            23h8m32s IN A   64.45.207.193
> ;; AUTHORITY SECTION:
> thebird.org.            23h8m32s IN NS  omar.hosting-network.com.
> ;; ADDITIONAL SECTION:
> omar.hosting-network.com.  23h15m56s IN A  12.24.176.250
>
> Gerald Waugh
> http://FrontStreetNetworks.Com