BudMan, on 03 March 2013 - 18:08, said:
So if i am reading this right you have some server you need to access, so this server is not available via the public dns? There is no name I could resolve on the internet that would point to this IP of the server.
So your creating entries in your host file to access this server?
What is this entry?
So your clients that your putting the host entry in use what for dns now? Are you going to point them at this new BIND server you want to bring up, so that you can resolve say google.com and neowin.net?
Where did this ddnsindia.com come from?? You do understand that domain is already registered on the internet and currently points here for the owning nameservers
Now can not see who its registered to because its whois info is listing DomainProtect, do you own this domain?
Be more than happy to walk you through how to setup bind, but not really clear on what your wanting to do.. So here is an example, lets say your server IP address you create host entries for is 192.168.1.100, and you call it www.myserver.tld
so you have a host entry like this
Is myserver this dnsindia domain? Or something else. Lets say you point to googledns now or your isp for dns currently. Just because you bring up a BIND that is setup to own the myserver.tld zone. Your clients are not going to ask him for dns -- they are going to ask googledns or your isp, etc.
So you need to point all your computers to your bind box, then you need to setup bind resolve the zone you want myserver.tld - and also forward other queries to googledns or your isp, etc.
So No if you want to resolve www.myserver.tld it can not be a caching only server, it would have to have authoritative zones, one being the myserver.tld zone - and then either query root servers for internet domains, or forward to some other dns so you can resolve say www.neowin.net, etc.
There is nothing that wrong with that SOA statement from how you presented it - your saying the SOA for dnsindia.com is a record called root.dnsindia.com -- but that is not really true.
The current SOA for that domain is
;; QUESTION SECTION:
;dnsindia.com. IN SOA
;; ANSWER SECTION:
dnsindia.com. 86400 IN SOA ns1.domainrecover.com. dnsmaster.domainrecover.com. 2011111400 28800 7200 604800 86400
So do you own that dnsindia.com domain or not - you shouldn't just grab some random name that you don't own and try and use it. If you want to use FQDN on your local network, then use domains that are not publicly feasible, ie make up the TLD, use .lan or .local, etc. For example you could use dnsindia.lan as you domain.
I am very much grateful for your answers.... Thanks !!.
Entries in the host files:
So now, I changed the name from dnsindia.com to dnsindia.inc
I was able to setup zone file for my internal network. i.e I am able to dig / ping the internal hostnames just fine.(local IPs)
There is a website at remote location that has public IP (66.xx.xx.84)
Now when I point www.myserver.tld to public IP in zone file, it does not gets resolved.
Zone file entries as :
@ IN NS ns1.myserver.tld
www.myserver.tld IN A 66.xx.xx.84
Do we need to include views for accessing Public IPs through local DNS?
The zone file looks fine for myserver.tld. checkzone command indicates the zone file as OK.
Please shed some light here sir