"The Hostname contains invalid characters" Namecheap with v2.1

kejianshi

Why would anyone use a name with @. in it? Accident?

JohnnyBeGood

Why would anyone use a name with @. in it? Accident?

I'm trying to update mydomain.com not just test.mydomain.com that's why @ is needed.


Namecheap
Note: To update an @ record, use @.yourdomain.com for the hostname.

https://doc.pfsense.org/index.php/Dynamic_DNS

kejianshi

Ahhhhhh… :D

JohnnyBeGood

@kejianshi:

Ahhhhhh… :D

I'm hoping this is easy fix. It would really suck if this was overlooked with v2.1 :(

jimp

There was a discussion here on the forum about this already with a workaround. Search the forum a bit and you'll hit it.

JohnnyBeGood

@jimp:

There was a discussion here on the forum about this already with a workaround. Search the forum a bit and you'll hit it.

Thank you so much for the reply. Knowing there's a workaround I will definitely take a deeper look.

borgotech

Hi,
i think u can take a look at my post http://forum.pfsense.org/index.php/topic,66769.0.html and u will find a solution as i find. Try to add separate entries for your hosts ex: domain.com (without @);host1.domain.com;host2.domain.com) with @domain.com i think Namecheap is updating all your records(i'm not sure because i'm using DNSExit).Try separate entries to see if works.

King Regards

kejianshi

Where is my face-palm icon… I'm not smart enough to have tried anything else. That would have been my first choice.

JohnnyBeGood

@kejianshi:

Where is my face-palm icon… I'm not smart enough to have tried anything else. That would have been my first choice.

I was searching thru the forums thinking there was better solution to update all at once like it was before.
At least I know what's the solution.
Thanks!

kejianshi

Yeah - I always updated 1 by one, but thats mainly because I didn't know to do it the other way. :P

Brute force and ignorance usually works.

Trel

@jimp:

There was a discussion here on the forum about this already with a workaround. Search the forum a bit and you'll hit it.

Is the workaround you're referring to, the one I'm currently doing with the cron job, because I was really hoping this was going to be fixed in 2.1 but it's still not working for me either.