stop zone transfers from coming in

My server works as a secondary for a zone. I asked the master server's admin to stop the zone transfer; I didn't get any reply and thus commented out the zone's section in my named.conf. But I'm still getting zone files coming in to my server. Here is what I have commented out: # zone "example.c

More than four name server for whois record

I cannot put more than four name servers in the domain management web interface (whois record). But in my zone file I already have more than four NS listed. Is there any way I can publish more than four domains in my whois record? ___ bind-users mailing l

Bind open to query from anyone

I've setup a secondary name server which works as a secondary or slave name server for my zone or domain name. However, I have tested and noticed that I can query for non-authoritative answers from my secondary or slave name server from outside my network. That is, any one can use my name server to

cache poisoning counter-measures

I'm trying to implement some basic counter-measures against the Kaminsky bug. I have had to configure my switch to allow any incoming query to TCP and UDP port 53 on my slave DNS server. I was wondering if this is going to cause any problem as far as security is concerned. Bind version 9.4.1 runni

Query SOA for serial number in split DNS

I'm trying to write a program (either in Perl or C) which will query my DNS servers to get the SOA of specific domains. But my primary NS uses split DNS and my IP address cannot query the external view. When I query, I only get the serial number of the internal view. Is there any way to query the

Re: setup default DNS server with only one record

On Fri, Dec 12, 2008 at 4:26 AM, Jonathan Petersson wrote: > You want to manipulate the "." zone. The config you have should be valid, > just point your "." zone in named.conf to the zone file. Thanks. This resolved the issue. This is what I did: edit named.conf and replace: zone "." in {

setup default DNS server with only one record

I am trying to setup a default DNS server for one of my restricted network segment so that no matter what people type in their browser, they will be redirected to a single IP address or the hostname. The zone file that I have setup is partially working - it resolves .mydomain.com to a single IP add

DNS Master server migration.

I'm migrating away from my 12 year old Solaris master DNS server to a new Linux based master server. I'm looking for suggestions on how to make the transition smooth without any downtime. The IP address of the new server will be different and so will be the hostname that will show up in the whois r