dns limits ..

[someone_4]

Is there a limit of Aliases that you can configure dns to see? I just configured dns with the parm file and hosts_to_named -f param wich made it from my /etc/hosts file.But all of the Aliases are not resolving. Also do I need to split up domains? If i have sub domains for example prod.networkip.net and admin.networkip.net. In my param file I just did networkip.net is it better to split them up? Also can I just edit the db files?

Richard

[Sridhar Bhaskarla]

As far as I know there is no limit on the number of aliases.

It is a good idea to keep subdomains like what you mentioned. This is more helpful
if you have different environments for the same application. Like production, development, testing etc.,. You can keep the same name and append the domain name to differentiate. Like app1.prod app1.dev app1.test etc.,

You can edit the db files. It's the fastest way of changing them. Just do a sighup to named.

-Sri

[Sanjay_6]

Hi Richard,

I don't think there is a limit on the number of aliases you can have for a system.

Here is a thread on how to configure aliases for a host.

http://us-support2.external.hp.com/cki/bin/doc.pl/sid=ea7f89e503248a08cf/screen=ckiDisplayDocument?docId=200000007951459

Hope this helps.

Regds

[someone_4]

ok ..By the way this is only an internal DNS .. anyways
I deleted all my files of my dns server /etc/named.data
and I rebuild everything.Then I went to my client .. and I could resolv some domains and not others. In my client I edited /etc/resolv.conf
I had these entries:
domain networkip.net
nameserver 192.168.10.4
search prod.networkip.net admin.networkip.net

I changed it to this
domain networkip.net
nameserver 192.168.10.4
#search prod.networkip.net admin.networkip.net

And now everything works .. all hosts and domains and alaises. When I uncomment search prod.networkip.net admin.networkip.net some stuff works and some doesnt.
Now I did build my dns with the param file with the only domain.
-d networkip.net

Even though we do have some servers on
prod.networkip.net
and some servers on
admin.networkip.net
But only used networkip.net is this ok? I mean it works but is this the proper way to set up dns?
Or should I have done
-d networkip.net
-d prod.networkip.net
-d admin.networkip.net

what is the main difference in using sub domains and just the main domain? And This did affect the client with the search line... How does all this tie in together?And what is the proper way to configure dns as far as domains and sub domains go.

Richard

[someone_4]

I think I answered my own question. ...
Now I rebuild the files in my dns server and did the -d options changed to
-d networkip.net
-d prod.networkip.net
-d admin.networkip.net

and I rebuild everything ..
Now I have
db.prod.networkip.net
db.admin.networkip.net
db.networkip.net

Now .. in my resolv.conf on my cleint ..
With the
#search prod.networkip.net admin.networkip.net
commented out .. I was not able to see anything under the prod.networkip.net or admin.networkip.net domain. But I was able to see other misc servers that didnt specify a domian on the /etc/hosts file that I used on the dns server to build the dns files. UGG ..
ok so I uncommented out the
search prod.networkip.net admin.networkip.net
and now everything works. I can resolv
prod.networkip.net
admin.networkip.net
and
networkip.net
I see half way understand why this is working .. I have the basic concept but can someone tell me in more detail .. why this is working the way it is?
I see that split up it is nicer and it seems to be organized better in the /etc/named/data dir in the dns server. But once again is this the ideal way to do internal dns? or the other way with just the
networkip.net domian??
If so why? And what does the seach option do in resolv.conf. How does all this tie in?? I am right there and I just need someone to push me over the line to complete understanding of dns.

Richard

[Sachin Patel]

Hi Richard,
Search doman1 doamin2.
Now whenever your system search for any name it will first looks in to the domain1 then in to the domain2.

I think it will be good idea if you use forwarder statment in to the /etc/named.conf file.
forwarder ip_1 ip_2

i.e if you can't resolve name using local dns then go to ip1 then to ip2 etc....

use sig_named restart to reload the db files.

As someone says directly edit your db file works great. Don't forget to increase serial number when you made any change.

If you do not have large number of systems then I think it is better if you use one domain. why? simplicity, easy to administer.

Sachin