On Sun, 9 Jan 2011 10:56:24 -0500, Tony Graziano wrote:
> this is correct. it does not have any of the pf6 stuff in it.

Right, I then take that, copy it to my public dns servers and add the 
additional records, in this case, the pfsense entry point. That's why it shows 
up in there. It's been working this way for remote access for quite some time 
but I thought it looked weird to me so wanted to check. Other than how I've got 
it set up and the rr record, I'm not really sure how it should look I guess.



 
> On Sun, Jan 9, 2011 at 10:46 AM, [email protected] <[email protected]> 
> wrote:
>> So is this the expected sipx output for the dns test or am I entering a
>> host name when building the server which I should not?
>> 
>> 
>> On Fri, 7 Jan 2011 18:31:28 -0600, [email protected] wrote:
>>> On Fri, 7 Jan 2011 19:05:31 -0500, Tony Graziano wrote:
>>> 
>>>> If the domain is mydomain.com and the hostname is uc.mydomain.com
>>>> then the
>>>> RR are wrong, very wrong. Are you suggesting sipx produced those?
>>>> 
>>> This is what sipx is generating when I use the DNS advisor. The DNS
>>> record
>>> I posted is my private DNS server where I used the sipx output and my
>>> own
>>> settings for various servers, edited to post here on the list.
>>> 
>>> 
>>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>>  Call Routing for SIP domain 'mydomain.com'
>>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>> 
>>>  NAPTR record for SIP TCP mydomain.com
>>>      priority: 2  weight: 0
>>>      protocol: "SIP+D2T"  regex: ""  uri: _sip._tcp.mydomain.com
>>> 
>>> mydomain.com.           IN      NAPTR   2 0 "s" "SIP+D2T" ""
>>> _sip._tcp.mydomain.com.
>>> 
>>>  NAPTR record for SIP UDP mydomain.com
>>>      priority: 2  weight: 0
>>>      protocol: "SIP+D2U"  regex: ""  uri: _sip._udp.mydomain.com
>>> 
>>> mydomain.com.           IN      NAPTR   2 0 "s" "SIP+D2U" ""
>>> _sip._udp.mydomain.com.
>>> 
>>>  SRV record for domain SIP TCP mydomain.com
>>>      priority: 1  weight: 0  port: 5060  server: uc.mydomain.com
>>> 
>>> _sip._tcp.mydomain.com. IN      SRV     1 0 5060 uc.mydomain.com.
>>> 
>>>  SRV record for domain SIP UDP mydomain.com
>>>      priority: 1  weight: 0  port: 5060  server: uc.mydomain.com
>>> 
>>> _sip._udp.mydomain.com. IN      SRV     1 0 5060 uc.mydomain.com.
>>> 
>>>  SRV record for service SIP TCP rr.uc.mydomain.com
>>>      priority: 1  weight: 0  port: 5070  server: uc.mydomain.com
>>> 
>>> _sip._tcp.rr.uc.mydomain.com. IN      SRV     1   0 5070
>>> uc.mydomain.com.
>>> 
>>>  SRV record for XMPP SERVER TCP mydomain.com
>>>      priority: 1  weight: 0  port: 5269  server: uc.mydomain.com
>>> 
>>> _xmpp-server._tcp.mydomain.com. IN      SRV     1  0 5269
>>> uc.mydomain.com.
>>> 
>>>  SRV record for XMPP CLIENT TCP mydomain.com
>>>      priority: 1  weight: 0  port: 5222  server: uc.mydomain.com
>>> 
>>> _xmpp-client._tcp.mydomain.com. IN      SRV     1  0 5222
>>> uc.mydomain.com.
>>> 
>>>  SRV record for XMPP SERVER CHAT ROOM TCP mydomain.com
>>>      priority: 1  weight: 0  port: 5222  server: uc.mydomain.com
>>>      NOTE: the XMPP client port is used here as this is the port used
>>>            by openfire to service multi-user chat requests.
>>> 
>>> _xmpp-server._tcp.conference.mydomain.com. IN      SRV     1  0 5222
>>> uc.mydomain.com.
>>> 
>>>  SRV record for XMPP CLIENT CHAT ROOM TCP mydomain.com
>>>      priority: 1  weight: 0  port: 5222  server: uc.mydomain.com
>>> 
>>> _xmpp-client._tcp.conference.mydomain.com. IN      SRV     1  0 5222
>>> uc.mydomain.com.
>>> 
>>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>>  IP Addresses
>>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>> 
>>>  A record for uc.mydomain.com
>>> 
>>> uc.mydomain.com.       IN      A       192.168.1.220
>>> 
>>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>> 
>>> 
>>> _______________________________________________
>>> sipx-users mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>> 
>> 
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/


_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to