DNS server configuration - root of the domain howto?
Hi, I need to prepare a DNS server as master for our domain. So far I succeed to do whatever I need, but do not know how to assign an IP address for the root of the domain, i.e. I know how to do serv1.mydomain.com, serv2.mydomain.com, etc., but how do I assign IP for "mydomain.com" only? Thanks -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition.
On 5/22/06, Sunny <sloncho@gmail.com> wrote:
Hi, I need to prepare a DNS server as master for our domain. So far I succeed to do whatever I need, but do not know how to assign an IP address for the root of the domain, i.e. I know how to do serv1.mydomain.com, serv2.mydomain.com, etc., but how do I assign IP for "mydomain.com" only?
Thanks
Or .. better yet, can I "forward" some of the internal name resolutions to any of the forwarders? I.e. my ISP takes care of some of our "publicly" known names, like www.mydomain.com, mail.mydomain.com, etc. I want to implement a DNS server only for internal use, so my internal networks can find servers on different internal networks (DMZ, etc.) by name. I do not want to change the domain name. So, is it possible, and how to do this? Like - just to add names, which are NOT publicly visible, and are just for inhouse use. Thanks -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition.
Sunny wrote:
I.e. my ISP takes care of some of our "publicly" known names, like www.mydomain.com, mail.mydomain.com, etc. I want to implement a DNS server only for internal use, so my internal networks can find servers on different internal networks (DMZ, etc.) by name. I do not want to change the domain name. So, is it possible, and how to do this? Like - just to add names, which are NOT publicly visible, and are just for inhouse use.
If I've understood correctly, you'd like "mail.mydomain.com" to be resolved externally (by your ISPs name-server), but "sunny.mydomain.com" to be resolved internally by your own name-server? You could always just run your own local server that would resolve all the names you want for "mydomain.com". Of course, you'd have to keep your internal and external name-servers in sync, but that's not too complicated. /Per Jessen, Zürich
On 5/23/06, Per Jessen wrote:
Sunny wrote:
I.e. my ISP takes care of some of our "publicly" known names, like www.mydomain.com, mail.mydomain.com, etc. I want to implement a DNS server only for internal use, so my internal networks can find servers on different internal networks (DMZ, etc.) by name. I do not want to change the domain name. So, is it possible, and how to do this? Like - just to add names, which are NOT publicly visible, and are just for inhouse use.
If I've understood correctly, you'd like "mail.mydomain.com" to be resolved externally (by your ISPs name-server), but "sunny.mydomain.com" to be resolved internally by your own name-server?
You could always just run your own local server that would resolve all the names you want for "mydomain.com".
Of course, you'd have to keep your internal and external name-servers in sync, but that's not too complicated.
/Per Jessen, Zürich
Yes, that's what I want. Just had a hope that I can cascade the resolution with master/slave servers, so I do not need to keep them in sync, i.e.: ISP DNS provides www, mail, etc. (publicly known names). Then, I would like to have one internal server at my COLO, which adds some internal names, like dmz1, dmz2, etc. And then I want to have in my office another DNS server, which is slave to the COLO one, and adds names for office computers. As I have VPN connection between the office and the COLO, I need the office machines to be able to resolve the COLO ones, but COLO machines do not have to know about office ones. As well as external users do not need to know about the internals at all. Anyway, looks like impossible, so I'll live with COLO DNS server knowing everything :) and trying to keep in sync with the ISP's DNS. And will make the office DNS server a slave of the COLO one. -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition.
Sunny wrote:
Yes, that's what I want. Just had a hope that I can cascade the resolution with master/slave servers, so I do not need to keep them in sync, i.e.:
ISP DNS provides www, mail, etc. (publicly known names).
Then, I would like to have one internal server at my COLO, which adds some internal names, like dmz1, dmz2, etc.
You _can_ do that by using multiple views, but that requires that your own name-server is the master, not your ISPs nameserver. /Per Jessen, Zürich
On 5/23/06, Per Jessen wrote:
Sunny wrote:
Yes, that's what I want. Just had a hope that I can cascade the resolution with master/slave servers, so I do not need to keep them in sync, i.e.:
ISP DNS provides www, mail, etc. (publicly known names).
Then, I would like to have one internal server at my COLO, which adds some internal names, like dmz1, dmz2, etc.
You _can_ do that by using multiple views, but that requires that your own name-server is the master, not your ISPs nameserver.
/Per Jessen, Zürich
Thanks Per, going the long way then :) Cheers -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition.
Sunny wrote:
I need to prepare a DNS server as master for our domain. So far I succeed to do whatever I need, but do not know how to assign an IP address for the root of the domain, i.e. I know how to do serv1.mydomain.com, serv2.mydomain.com, etc., but how do I assign IP for "mydomain.com" only?
Here's an example: $TTL 86400 ; 24 hours $ORIGIN jessen.ch. @ IN SOA ns1.enidan.ch. hostmaster.enidan.ch. ( 2006051000 ; serial 28800 ; refresh (8 hours) 7200 ; retry (2 hours) 604800 ; expire (1 week) 86400 ; minimum (1 day) ) IN TXT "v=spf1 ip4:217.8.216.8/29 -all" IN NS ns1.enidan.ch. IN NS ns2.enidan.ch. IN MX 0 bulwark.spamchek.net. IN A 217.8.216.11 www IN CNAME jessen.ch. localhost IN A 127.0.0.1 /Per Jessen, Zürich
On 5/23/06, Per Jessen wrote:
Sunny wrote:
I need to prepare a DNS server as master for our domain. So far I succeed to do whatever I need, but do not know how to assign an IP address for the root of the domain, i.e. I know how to do serv1.mydomain.com, serv2.mydomain.com, etc., but how do I assign IP for "mydomain.com" only?
Here's an example:
$TTL 86400 ; 24 hours $ORIGIN jessen.ch. @ IN SOA ns1.enidan.ch. hostmaster.enidan.ch. ( 2006051000 ; serial 28800 ; refresh (8 hours) 7200 ; retry (2 hours) 604800 ; expire (1 week) 86400 ; minimum (1 day) ) IN TXT "v=spf1 ip4:217.8.216.8/29 -all"
IN NS ns1.enidan.ch. IN NS ns2.enidan.ch.
IN MX 0 bulwark.spamchek.net.
IN A 217.8.216.11 www IN CNAME jessen.ch.
localhost IN A 127.0.0.1
/Per Jessen, Zürich
Thanks Per, would you tell me which exact line defines the resolving of the host without anything before the domain name? Looks like I can not understand :) -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition.
participants (2)
-
Per Jessen -
Sunny