Server ignore ns change

[Jonathan Petersson]

master seeds our internal slaves with our internal zone.
no clients can do lookups via the master neither towards the zone nor
recursive.
all the slave servers are recursive and acts as a slave for out internal
zone
there's not authorative server in the zone
I don't see it how the server config would affect this since this seams to
be a client side issue.

On Wed, May 14, 2008 at 1:44 PM, Kal Feher <kal.feher at melbourneit.com.au>
wrote:

> I¹m replying to the list so that others may also assist.
> I don¹t wish to be pedantic and I realise that English is not the first
> language of many on this list, however your references to master and slave
> are not consistent with a cache server configuration. I¹m more confused by
> the fact that some of your servers are recursive and others not. Your
> answers actually make it sound like you are referring to an internally
> hosted domain, not recursive lookups on behalf of clients.
>
> Please clarify the above. Be as explicit as possible, basic information
> wont
> hurt us, but missing information will hurt you (or at least prevent us from
> helping you).
>
> Make sure you reply to the list as well, since there are definitely smarter
> people than I that read these posts.
>
> On 14/5/08 7:32 PM, "Jonathan Petersson" <jpetersson at garnser.se> wrote:
>
> >
> >
> > On Wed, May 14, 2008 at 10:19 AM, Kal Feher <
> kal.feher at melbourneit.com.au>
> > wrote:
> >> I am assuming that both the old and new servers are caching name servers
> not
> >> authoritive (as this might indicate a delegation issue).
> > Correct.
> >>
> >>
> >> Starting from the most basic:
> >> Which ip addresses are hitting your old servers?
> >> Check those hosts for their current config (perhaps you missed a few in
> your
> >> cut over?).
> >> Is it only DHCP hosts that are hitting your old servers or even
> statically
> >> configured hosts?
> > It's both DHCP and statically hosts. (Linux hosts)
> >>
> >>
> >> Check that your new servers arent forwarding requests to the old
> servers.
> >> I've seen this in the past when a testing config wasn't removed from
> servers
> >> put into production.
> > Each server is indepentent and doesn't rely on others (except the master
> > feeding them).
> >>
> >>
> >> If the above doesn't point you in the right direction then you'll need
> to
> >> provide more information regarding the exact configuration of your
> network
> >> and dns servers.
> >
> > We've 1 primary master that feeds all of our slaves. Our master has
> recursion
> > disabled but all slave name-servers has recursion enabled. We don't have
> any
> > authoratitive servers for the domain, I'm not sure why this is, the last
> admin
> > didn't have any good answer for it.
> >
> >>
> >>
> >>
> >> On 14/5/08 7:02 PM, "Jonathan Petersson" <jpetersson at garnser.se> wrote:
> >>
> >>> > Hi.
> >>> > We recently introducted two new dns server in our networks removing
> our
> >>> old
> >>> > ones from the DHCP. I've updated the servers which had resolv.conf
> >>> > statically. Even though all servers is updated I'm still getting most
> >>> > requests to my old servers.
> >>> >
> >>> > If I do a dig the new servers answers.
> >>> >
> >>> > What could the reason for this be?
> >>> >
> >>> > Thanks
> >>> >
> >>> > /Jonathan
> >>> >
> >>> >
> >>> >
> >>
> >> --
> >> Kal Feher
> >>
> >>
> >>
> >
> >
>
>
> --
> Kal Feher
>
>
>
>