Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Skydiver on March 24, 2005, 08:04:28 AM
-
The format for a SVR RR is this:
_service._protocol SVR Priority Weight Port hostname
In this case i want to establish an entry for our primary SIP server, gateway.mydomain.com, that will listen on UDP port 5060
_sip._udp SRV 0 0 5060 gateway.mydomain.com
_______________________________________________
BIND rpms are installed
_______________________________________________
I need to configure the named.conf file
// Default named.conf generated by install of bind-9.2.4-5_EL3
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
};
include "/etc/rndc.key";
___________________________________________________
Then i guess i need to create a zone file.
Placement of the new resource record is important. Here is a sample zone file:
; zone 'mydomain.com' last serial 1998071308
$ORIGIN com.
mydomain 86400 IN SOA gateway.mydomain.com. postmaster.mydomain.com. (
1998111908 ; Serial
36000 ; Refresh
900 ; Retry
36000 ; Expire
28800 ); Minimum
IN NS gateway.mydomain.com.
IN NS ns3.backupdomain.com.
IN MX 1 gateway.mydomain.com.
IN A 192.168.0.1
;If we place the SRV record above the next line it fails to load
$ORIGIN fitawi.com.
_sip._udp SRV 0 0 5060 gateway.mydomain.com.
gateway IN A 192.168.0.1
www IN CNAME gateway.mydomain.com.
After reloading the zone file I can verify that the entry is working by using dig.
_______________________________________________
The zone file is confusing me anyone have hints on best way to complete this.
Cheers
Greg
-
well I was under impression that SME since version 5.6 uses dnscache/tinydns for dns needs...
search this forum for tinydns and there was a tutorial hot to do that on 6.x - so I do believe it may work on SME7a3 (or 4 or whatever) as well
or I am not understanding what you want to achieve...
-
Not sure this will work without some manual file manipulation. I was using a SME 6 box for a long-term temp. DNS server. It would not answer authoratively for any domain I setup on it. I ended up building a debian "woody" server just for DNS. It works great.
Just my experience.
-
well I was under impression that SME since version 5.6 uses dnscache/tinydns for dns needs...
It does. Note also that tinydns's data isn't publicly visible, but I'm not sure whether skydiver wanted to publish globally or just to the LAN.
I strongly discourage anyone from publishing DNS globally unless they really know what they are doing. And before using bind, take a look at its security record.
-
Im not sure i need to do this anymore as i have a DNS server (public) redirecting the domain to my public ip address this really should be enough. Any see a reason why i would need to have my own DNS server?