umm... eh? my DNS is whacko...
Moderator: Moderators
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
I'm probably not going to be staying with BIND forever; since all of the zone data comes out of databases and it has to rebuild really big BIND files when the database changes, I'm looking at other DNS servers that may have better integration with a backend database. Either way, BIND will be fixed or something else (that hopefully doesn't have the same bugs) will take its place.
I prefer real time systems rather than "wait 15 minutes" or "wait an hour" stuff. The goal is to get the DNS changes commited to second you change it in the account manager.
I prefer real time systems rather than "wait 15 minutes" or "wait an hour" stuff. The goal is to get the DNS changes commited to second you change it in the account manager.
Technical Support support@rollernet.us
Roller Network LLC
Roller Network LLC
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
i believe the prob was this: when ns1/ns2.rollernet.us saw the notify, they made a winbots.org SOA request to the master.... who didnt serve that domain on udp (it is stealthed, it only served up TCP AXFR requests), so it got an error... the reason bind checked in with the SOA record, i believe, was to see if the s/n had been incremented since its last get.... and was assuming if it hadnt been incremented, then that meant that it had the latest copy and didnt need to do an axfr...