[prev in list] [next in list] [prev in thread] [next in thread]
List: bind-users
Subject: Re: bind 9 error
From: Mark_Andrews () isc ! org
Date: 2003-05-29 23:47:38
[Download RAW message or body]
> Starting having the same problem with mci.com and a few others
> domains. Forwarded DNS off the old server and more than half the
> messages in the queue delivered.
>
> Is there any way to tell BIND 9 to not be so strict? No one is going
> to care about the long run if the short run doesn't work. Products
> should be backward compatible and as flexible as possible, but it
> seems BIND 9 is choosing the road of incompatible and strict.
Why do you think that it should work with misconfigurations
like below? It's not like it is a new requirement that the
glue in the parent has to match that in the child.
Mark
Parent:
mci.com. 2D IN NS dns1.wcom.com.
mci.com. 2D IN NS dns2.wcom.com.
Child:
mci.com. 16M IN NS dns1.mci.com.
mci.com. 16M IN NS dns2.mci.com.
Parent:
wcom.com. 2D IN NS dns1.wcom.com.
wcom.com. 2D IN NS dns2.wcom.com.
Child:
wcom.com. 16M IN NS omzdns.mcilink.com.
wcom.com. 16M IN NS dns1.mci.com.
wcom.com. 16M IN NS dns2.mci.com.
wcom.com. 16M IN NS ndcdns.mcilink.com.
Parent:
mcilink.com. 2D IN NS dns1.wcom.com.
mcilink.com. 2D IN NS dns2.wcom.com.
Child:
mcilink.com. 16M IN NS omzdns.mcilink.com.
mcilink.com. 16M IN NS dns1.mci.com.
mcilink.com. 16M IN NS dns2.mci.com.
mcilink.com. 16M IN NS ndcdns.mcilink.com.
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@isc.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic