Cname/alias for external domain
-
I cannot see how's a program expecting oldhostname.domaina.com going to respond to requests to newhostname.domainb.com.
-
I cannot see how's a program expecting oldhostname.domaina.com going to respond to requests to newhostname.domainb.com.
the program wont. when it looks to pfsense to connect out via the internet, pfsense will redirect it. basically, i'd like to enter a cname into pfsense.
-
I have no idea what "program" are we talking about here. If you expect that pfsense DNS record will rewrite e.g. www.google.com to www.bing.com in your browser URL bar, then it's not what's gonna happen.
-
I have no idea what "program" are we talking about here. If you expect that pfsense DNS record will rewrite e.g. www.google.com to www.bing.com in your browser URL bar, then it's not what's gonna happen.
on the client side (the program) it will use the original domain old.domaina.com
it is a cname, have you ever worked with cnames? that is what i am looking to do.
-
Your CNAME will not work if the program somehow works with the requested hostname. Once again, see example above… It won't work either if we are talking about some IP camera with a webserver.
-
Your CNAME will not work if the program somehow works with the requested hostname. Once again, see example above…
it works all the time in the scenarios where i am hosting my own domain and i can create a cname. it doesn't seem that i can do that in pfsense.
-
Well, that's awesome. How about reinstalling the broken thing instead of inventing similar nonsense like hijacking nonexistant hostname with a DNS forwarder?
-
Well, that's awesome. How about reinstalling the broken thing instead of inventing similar nonsense like hijacking nonexistant hostname with a DNS forwarder?
happens all the time with cnames, i guess it just isnt part of pfsense.
-
Fail to see why it should do any such thing in the first place. It's a DNS forwarder.
-
Fail to see why it should do any such thing in the first place. It's a DNS forwarder.
i wasn't referencing that section, specifically, just if pfsense could do it.
-
Sure; install tinydns or bind, or another authoritative DNS server. Neither dnsmasq, nor unbound. Or finally stop wasting the time and invest 5 minutes into reinstalling whatever broken thing you have there, instead of discussing for two days how to work around it.
-
Sure; install tinydns or bind, or another authoritative DNS server. Neither dnsmasq, nor unbound. Or finally stop wasting the time and invest 5 minutes into reinstalling whatever broken thing you have there, instead of discussing for two days how to work around it.
get the stick out of your ass.
if you don't want to help, that's fine with me.
i could have posted the question and gotten a reply 10 minutes later. there goes your two day comment.
also, had pfsense had this feature and someone posted about it, it would have answered my question and i could have used it for something else in the future.
-
@tomdlgns:
get the stick out of your ass.
Thanks for your kind "recommendation". Just found the ignore list feature, sanity restored. ::)
-
It's actually a valid question/use case. Ugly, sure. Not ideal? Certainly. But there are always devices you cannot control. Black boxes from vendors that won't update or would charge exorbitant fees to do so.
Unfortunately the way that CNAME records work in dnsmasq, the target of the CNAME must also be locally known. So you can CNAME something in /etc/hosts, but not something that would involve making a query to another remote DNS server. It's a limitation of dnsmasq, not DNS in general.
There is a more in-depth answer here:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2006q1/000583.htmlBut ultimately, to do that you'll need a much fancier DNS system.
If you happen to have a domain with Namecheap, their hosted DNS that you can manage in their control panel does support this function.
-
It's actually a valid question/use case. Ugly, sure. Not ideal? Certainly. But there are always devices you cannot control. Black boxes from vendors that won't update or would charge exorbitant fees to do so.
Unfortunately the way that CNAME records work in dnsmasq, the target of the CNAME must also be locally known. So you can CNAME something in /etc/hosts, but not something that would involve making a query to another remote DNS server. It's a limitation of dnsmasq, not DNS in general.
There is a more in-depth answer here:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2006q1/000583.htmlBut ultimately, to do that you'll need a much fancier DNS system.
If you happen to have a domain with Namecheap, their hosted DNS that you can manage in their control panel does support this function.
thank you, this is helpful, in that, it is a better response as to why it won't work.
the current domain/old domain i started the thread about is an expired dyndns hostname.
the client side program is using olddomain.gotdns.com and that name is no longer valid on their network. i don't want to get into why it isnt valid anymore, that isn't the point. however, that is what prompted me to ask the question in this forum.
yes, reinstalling the software will work, but sometimes finding another way around the problem is fun due to the challenge involved.
thanks for the reply, jimp.
-
Great, I have learned too :D
-
Does anyone know if this is possible now? This is useful in cases where you'd want to re-direct a URL to a reverse proxy.
-
No, you still cannot make a CNAME to an external hostname using built-in tools.
-
Hello, any news on that?
I try also to do the same to filter youtube.com content based on this docs:
https://support.google.com/youtube/answer/6214622?hl=enThanks for your help
-
I'm also trying to figure out how to configure pfsense to use the youtube filters:
https://support.google.com/youtube/answer/6214622?hl=enIf anyone has another approach I'd love to hear it.
Thanks
- Jon
