Currently Being ModeratedOct 31, 2012 4:06 AM (in response to chaffers)
I'm unfamiliar with that user interface so I'm not entirely clear on what it's showing, however, your screenshot seems to indicate that the TXT record is named 'webiste' instead of 'website'. For your example to work, you should have a PTR record named '_http._tcp.up.com' with a target of 'website._http._tcp.up.com'. The SRV and TXT records should be named 'website._http._tcp.up.com'.
Currently Being ModeratedOct 31, 2012 5:25 AM (in response to AndrewTJ)
thanks for the quick reply AndrewTJ - I did notice the typo after posting and corrected however the problems remains. below is the contents of my up.com.dns file - i can see nothing out of place but cannot get a resolution
; Database file up.com.dns for up.com zone.
; Zone version: 22
@ IN SOA dns1.up.com. hostmaster.up.com. (
22 ; serial number
900 ; refresh
600 ; retry
86400 ; expire
3600 ) ; default TTL
; Zone NS records
@ NS dns1.up.com.
; Zone records
_http._tcp.up.com. PTR website._http._tcp.up.com.
website._http._tcp.up.com. TXT ( "txt path=/" )
SRV 0 0 80 dns1.up.com.
_services._dns-sd._udp.up.com. PTR _http._tcp.up.com.
b._dns-sd._udp.up.com. PTR @
lb._dns-sd._udp.up.com. PTR @
dns1.up.com. A 192.168.1.153
Currently Being ModeratedOct 31, 2012 6:06 AM (in response to chaffers)
That looks okay. It's likely that the previous nodata response has been cached for the SOA minimum value (default TTL in your zone print out). While you're testing it might be worth dropping both the SOA minimum and the TTL of the service discovery records to one. I'm not sure how to flush the DNS cache on an iOS device but perhaps toggling Airplane mode or rebooting the device will get you going?