Search results for query: *

You can run a dig command to see if the zone is allowing zone transfers: dig @"customer DNS server" domain.com xfer If you have permissions you will see the whole zone, normally on internet facing DNS servers, zone transfers are turned off.

When the client looses the geteway the next time, before you do a release and renew, type in ipconfig /all. Check that the DHCP server is the correct one and not a rouge server handing out addresses.

The first thing you need to do is to change the CNAME records you have to the following: 1 IN CNAME 1.0-63.123.123.99.in-addr.arpa. 2 IN CNAME 2.0-63.123.123.99.in-addr.arpa. And in your 123.123.99.in-addr.arpa zone file you will need to add the following NS records...

Check out the Cisco CSS 11000 Switch on http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_tech_note09186a008009432f.shtml

There are no preferences in DNS for any records that will do that except for MX records. It’s the mail server that will move to the next preference if the lowest one is not reachable not. There are hardware products that will do what you want.

Each of your VPS sites has a public IP address, for example VPS1 could have an address of 77.77.77.10 and VSP2 have an address of 77.77.77.20. VPS1 is hosting www.example1.com and VPS2 is hosting www.example2.com. DNS just answers queries about the sites with the IP address. On both the primary...

There is no good reason to configure your name servers having ns1 be primary for one zone and ns2 primary for another. Make one (ns1) server the primary server for all your zones and ns2 secondary for all the zone on the primary. Load balancing is not done by making one a secondary or primary...

If you are using only one view statement then all the zones must be included in that view, otherwise you will have to create an additional view for the external view, but either way when you use views all your zones have to be inside a view.

I believe what you want to do is to delegate the abc.xyz.mycompany.org to a different DNS server for resolution. To do that you need to put an NS (Name Server) record in the DNS server that is authoritative for xyz.mycompany.org. Add the following record to you xyz.mycompany.org DNS server...

Smah is correct if you can ping, tracrt or nslookup mydomain.com and you resolve correctly the problem is in your IIS server. If you do not resolve correctly try adding an additional A record to mydomain.com like the following: @ IN A <IP Address>

Good catch, I missed both periods. So the record should be: childdomain.parentdomain.com. IN NS mydnsserver.com. or childdomain IN NS mydnsserver.com.

You need an NS record in the parent domain to delegate the child domain. In the parent domain you will need to add a record like the following: childdomain.parentdomain.com IN NS mydnsserver.com mydnsserver is where the child domain is load.

I would try the Dig utility and use the trace switch like in the following command. dig @10.10.10.10 something.org +trace where 10.10.10.10 is the address of your DNS server. This will show the steps the resolver went through to get the answer. I would restart the DNS server and run the...

You will have to configure the IP Helper(DHCP Relay) on the Cisco switch to forward the discovers for the clients on one VLAN to the DHCP server VLAN.

They do make changes to the Root Servers from time to time, so its a good idea to download the latest. You can find the latest version at the following link. http://www.iana.org/popular.htm.

If you have the IP Helper(DHCP relay) set correctly to forward DHCP packets to your DHCP server, then when packets arrive at the DHCP server the giadder will be filled in with the VLAN where the packet came from and the DHCP server hand out and address for the correct VLAN.

Check that you have DHCP relay set to the correct address on your routers. You may be still sending the DHCP traffic to the 2000 servers addresses.

Sorry for the delay. Check the syntax in the secondaries.include file. How many zone are in this file? The error looks like there is a missing "}".

I need more of the named.conf file. The error states that the problem is in line 47 of named.conf or close to it. /etc/named.conf:47.

When you started BIND on the slave did you start it as Root, does it have the privileges to create a file in the directory where the zone file will be copies to? You can test to see if the slave can do a zone transfer by doing the following command: dig @1.1.1.1(address of the master)...