PIAF In A Windows Domain - FQDN? DNS SRV?

[rideabike]

When setting up Nortel 1535s, the Nerd Vittles "2010 Bargain of the Year..." article says to put in the FQDN of the Asterisk server.

Now you’re ready to configure your VoIP settings (Menu, Settings, VoIP Settings). Start with the domain of your server: sip2sip.info or the FQDN of your Asterisk server (Menu, Settings, VoIP Settings, Misc., Domain Name).

I'm in a Windows domain. How do I determine the FQDN of the PIAF PBX?

Also, do I need to create entries in the DNS server for the PBX? I am having trouble with some calls getting connected to the phones correctly and a suggestion was made that a DNS SRV record needs to be created or alias' need to be created on the PBX. Any ideas on whether or not this is necessary and do you have any tips on implementing the SRV or creating the alias'.

Thanks.

 

[atsak]

IN Windows Active Directory, the FQDN is setup when you create the domain controller. You can find this out lots of ways, either on the domain controller in AD Users and Computers (look at the domain name at the top of the tree in the MMC console), or on a client PC by looking at the domain suffix in ipconfig /all from a command prompt.

Typically people set these to something like domianname.lan or sometimes something.domainname.com (in other words setting it up as a subdomain of the business trading domain name), which has some advantages in that you can maintain an inside and outside DNS server, and have different IP's resolve differently depending on where you are. Some people don't like that way though, it's really a matter of administrator preference. You also can simply use a public DNS name like something.com if you like.

You should create an A record for the PBX to save some hassle in the AD integrated DNS server on the domain controller (typically). Otherwise, you'll need to use IP addresses to refer to the PBX in config files etc. for proper name resolution.

I don't do anything with SRV records or the like, though that's largely because I haven't needed them for any configuration requirements.