[NTLUG:Discuss] "Back up dns server"?

[m m]

> From: sysmail at glade.net> To: discuss at ntlug.org> Subject: Re: [NTLUG:Discuss] "Back up dns server"?> > On Tue, Dec 04, 2007 at 07:49:53PM +0000, m m wrote:> > All:> > > > We all know that we need to have two DNS server for a domain.Usually, these two DNS server have the same A records for a domain.All of this settings are preventing the web site (mail...) failure. > > > > Based on the concept above, I think we should be able to set the 2nd DNS server to a different IP with same domain name as primary DNS server.> > In this case, there is a need to run 2 servers with same domain but different IP. > > Not a problem, one dns server at 1.2.3.4 and another at 4.5.6.7, both> named dns.mydomain.com - but also not giving any redundancy.> > > Why is doing this? When one of the IP is not available, another one will be still available.> > > > Please note, this is not a web farm issue. I think this will be to fix IP (or firewall) "broken" issue. > > > > Firewall issues? Can you amplify on that? Seems like that would> different from DNS, unless there is NAT or something that you need to> play tricks with.
 
Sorry for the confusion, What I means is when the file setting is massed up, the request packets can not go to your server. for example: 
you have web site AAA.com with IP 1.2.3.4 on server BOX1, your DNS server have set up correctly. you server BOX1 is behind firewall, and your firewall knows to sent the traffic with IP 1.2.3.4 to BOX1. Everything at this point is good.
 
one day, something happened on yor firewall (device), it is dead and doesn't route the request packets to 1.2.3.4. This is what I mean firewall broken.
How do you keep yor AAA.com site still live at this point?
 
if we have the "another" dns server "says" AAA.com have another ip 1.2.3.5, will it solve the problem, right? 
this my question:
can we have one dns server says AAA.com's ip is 1.2.3.4 and
another dns server says AAA.com's ip is 1.2.3.5?
 
 > > An interesting point is the DNS servers referenced by name in whois> actually have no firm tie to the name servers that actually serve your> domain. Whois and DNS are not connected. Whois does not need to have> valid name servers listed for your DNS to work without trouble - but you> certainly should try to keep whois current for your domain.> > To find xyz.com, a DNS client will first ask one of the root servers,> taken for granted from the client's 'hints' file, for who has authority> for '.com'. Then the client will ask one of those servers who has> authority for 'xyz.com'. Then, the client will ask one of those servers> for the 'A' record (or whatever you are looking for). The process will> continue if the authority is further delegated.> > Anyway, thought I would offer that - corrections welcome. Did I get> that process right?
I know this. but this is kind off my point.
 
> > Regards,> > Carl> > > Am I right? Any company doing such a "back up DNS server"?> > > > Thanks.> > _________________________________________________________________> > Share life as it happens with the new Windows Live.Download today it's FREE!> > http://www.windowslive.com/share.html?ocid=TXT_TAGLM_Wave2_sharelife_112007> > _______________________________________________> > http://www.ntlug.org/mailman/listinfo/discuss> > -- > > =================================================================> Carl Haddick> sysmail at glade.net> PO Box 1586> Mexia, TX 76667 Remember, Murphy was an optimist.> =================================================================> > _______________________________________________> http://www.ntlug.org/mailman/listinfo/discuss
_________________________________________________________________
You keep typing, we keep giving. Download Messenger and join the i’m Initiative now.
http://im.live.com/messenger/im/home/?source=TAGLM