[scoobydoobie]

How


Hey how's it going!

I'm in the process of setting up a little network and am wondering about name resolution on the internal side of things, see right now there is an openbsd router 192.168.1.1 and is running named doing only caching so on this machines

resolv.conf is
search router.domain.com
nameserver 127.0.0.1
nameserver 192.168.1.1

hosts is
127.0.0.1 router.domain.com
192.168.1.9 www.domain.com
192.168.1.11 mail.domain.com
etc.....

Now, on 192.168.1.2 client machine with browser has resolv.conf which
nameserver 192.168.1.1
worked! now not work?

but on 192.168.1.10 client machine with browsers works resolving domainname sortof other browser not standard ie:crappydoo
dns on this machine is 192.168.1.1

Basically I want too run all name resolution internally from a single point preferably the "router" without for the time being running authorartive dns.
All external requests find without a problem besides what has yet to be redirected.

Anyways thanks alot! any comments, suggestions appreciated

[elmore]

scoob! Welcome to SE! Hopefully we'll be of some use to you.

I wrote up a how-to for DNS a while back. It's a mini-how-to and isn't exaustive but if you're fimiliar with DNS to some extent it'll probably help you out.

Anyways, here's the link:

http://screamingelectron.org/phpBB2/viewtopic.php?t=246

Hopefully that'll help, if not just let us know and we'll get to working on another solution.

[scoobydoobie]

elmore thanks looks interesting will definetly give it a shot tomorrow.

>> Welcome to SE! Hopefully we'll be of some use to you.

:lol: yes some great stuff here, keep it up.

I'm new on openbsd and it is simply awesome :!:

[scoobydoobie]

well elmore I used that script and it did help understand what needed to be done so I got it working after doing it by hand.

here is what was done for Internal name resolution and caching DNS
Why: because to many internal machines to be messing around with everyones' resolv and hosts files.

named.conf

[code:1:1c028f4535]
options {
directory "/";

// Uncommenting this might help if you have to go through a
// firewall and things are not working out. But you probably
// need to talk to your firewall admin.

// query-source port 53;
};

controls {
inet 127.0.0.1 allow { localhost; } keys { rndc_key; };
};

key "rndc_key" {
algorithm hmac-md5;
secret "";
};

zone "." {
type hint;
file "root.hint";
};

zone "0.0.127.in-addr.arpa" {
type master;
file "internal/db.127.0.0";
};

zone "domain.com" in {
type master;
file "internal/db.domain.com";
};

zone "1.168.192.in-addr.arpa" in {
type master;
file "internal/db.192.168.1";
};

[/code:1:1c028f4535]


internal/127.0.0.1
[code:1:1c028f4535]

$TTL 3D
@ IN SOA ns.domain.com hostmaster.domain.com (
1 ; Serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns.domain.com.
1 PTR localhost.
[/code:1:1c028f4535]
internal/db.domain.com


[code:1:1c028f4535]
$TTL 3D
@ IN SOA ns.domain.com. postmaster.domain.com. (
199802151 ; serial, todays date + todays serial #
8H ; refresh, seconds
2H ; retry, seconds
4W ; expire, seconds
1D ) ; minimum, seconds
;
NS ns ; Inet Address of name server
MX 10 mail.domain.com. ; Secondary Mail Exchanger
;
localhost A 127.0.0.1
ns A 192.168.1.1
www A 192.168.1.9
mail A 192.168.1.11





[/code:1:1c028f4535]


internal/db.192.168.1

[code:1:1c028f4535]

$TTL 3D
@ IN SOA ns.domain.com. postmaster.domain.com. (
199802151 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns.domain.com.

1 PTR ns.domain.com.
9 PTR www.domain.com.
11 PTR mail.domain.com.

[/code:1:1c028f4535]

Later;