[cisco-voip] Can we resolve tftp option 150 via a DNS lookup

[FrogOnDSCP46EF]

thanks

On Thu, Nov 20, 2008 at 1:49 AM, Ryan Ratliff <rratliff at cisco.com> wrote:

>  Option 150 is specific to Cisco devices so I'm not surprised it's not in
> the DHCP RFC.
> Setting a hostname there should work as long as the phone is able to
> resolve it correctly.
>
>
> -Ryan
>
>
>  ------------------------------
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *FrogOnDSCP46EF
> *Sent:* Tuesday, November 18, 2008 10:01 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Can we resolve tftp option 150 via a DNS lookup
>
> Have anyone tried DNS server instead of Array to achieve redundancy?
>
> Let's say we've 2 x TFTP server for redundancy purpose.
> TFTP1 - 1.1.1.1
> TFTP2- 1.1.1.2
>
> normally TFTP redundancy is achieved by creating Array in DHCP. Put both
> TFTP server ip address in the DHCP.
> array: 10.1.1.1 10.1.1.2
>
> Instead of putting those IP address in the array in DHCP config can I put
> one DNS like name?
>
> Array: tftp1tftp2 or tftp.cisco.com
> In DNS - tftp.cisco.com has 2 hosts associated to it e.g. 10.1.1.1 and
> 10.1.1.2--
>
> The DHCP RFC tells that ICMP is the one which finds out TFTPS erver's
> subnet but no mention about DNS address for option 150.
>
>
> Smile, you'll save someone else's day!
> Frog
>



-- 
Smile, you'll save someone else's day!
Frog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081120/07e6b9c0/attachment.html>